From Add Item in Template Maintenance select the Extension history button shown here. |
Extension history usually means "order history" but can be more general purpose than this. An extension history is associated with a either a customer or a location, and adding an extension history item to a template allows this history of orders etc. to be viewed by the user. In a typical "order history" scenario, the order history will show the date of the order, an order number and the associated order lines and prices.
The extension history can either be populated by an external system or it can be automatically populated based on Table items of submitted forms. For more information on this please see the Order history workflow action. |
Unable to show how an Extension history item might look on a device. |
Main |
Main screen for creating/amending an Extension history item |
Main screen for creating/amending an Extension history item |
|||||||
| *Question | This is the text “label” that is specifying the information that needs to be entered or the question to be answered. Although this is not necessarily a question in all cases, Question is used as the general term to cover the text shown next to an input field. The text should be as short as possible whilst still being self-explanatory. Over-long questions take up a lot of space on PDA screens with their restricted size, so try and make them concise. This text should be an aid to help guide the user through the screen. Any more explanatory text can be made available as “Auditor’s notes” or “Full question text”. | ||||||||
| *Entity type | Extension histories can be associated with customers or with locations. Depending on which of these histories you wish to show, choose the entity type that is required. | ||||||||
Advanced |
Advanced features of an Extension history item. |
Advanced features that can be applied to an Extension history item. |
|||||||
| Item flag |
Template item flags are used to apply display classes to template item in a consistent and efficient way. They are set up in a system list called Template item flags and might be given names such as Danger so the text appears in red, Disclaimer for smaller text, Long answer to give extra space to the answer. This means that changing the display class can be done in one place rather than on all template items. |
||||||||
| *Unique name |
A unique name must exist for everything in a magic5 template. It is so important that magic5 pre-fills the prompt with a non-meaningful name which it will use by default. This does not need to be changed. However, if the data associated with the unique name is to be used elsewhere (for example as part of a calculation, imported or exported, or carried over to a new job), it is helpful to use a meaningful name (such as RefNo, QuantityOrdered, ItemTotal, ContactName, ReasonForReferral) and this meaningful name must be entered before the template is used with real data. If the unique name is changed at a later date, existing data will not be lost but it may no longer be accessible by magic5, in which case it cannot be displayed, used in calculations or exported. It is therefore recommended that this is done only as a last resort and that the original template is duplicated before changes are made - this means that existing data can still be retrieved if necessary. If in any doubt, please contact magic5 support for the best way to deal with this. |
||||||||
|
|||||||||
